Skip to content

Add namespace to Nexus operation info#1416

Open
Quinn-With-Two-Ns wants to merge 3 commits intotemporalio:mainfrom
Quinn-With-Two-Ns:NEXUS-283
Open

Add namespace to Nexus operation info#1416
Quinn-With-Two-Ns wants to merge 3 commits intotemporalio:mainfrom
Quinn-With-Two-Ns:NEXUS-283

Conversation

@Quinn-With-Two-Ns
Copy link
Copy Markdown
Contributor

@Quinn-With-Two-Ns Quinn-With-Two-Ns commented Apr 6, 2026

What was changed

Add namespace to Nexus operation info

Why?

So an operation handler knows what namespace it is in, we already include this in other SDKs, was just missed in Python

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

Note

Low Risk
Low risk, additive metadata change that threads the worker namespace into Nexus operation context and adds coverage via a new integration test.

Overview
Nexus operation handlers can now access the worker’s namespace via nexus.info() by extending Info with a namespace field and wiring it through _NexusWorker when setting start/cancel operation contexts.

Adds a new workflow-based test ensuring nexus.info() returns both namespace and task_queue for an operation executed via a Nexus endpoint.

Reviewed by Cursor Bugbot for commit 3413168. Bugbot is set up for automated code reviews on this repo. Configure here.

@Quinn-With-Two-Ns Quinn-With-Two-Ns requested a review from a team as a code owner April 6, 2026 21:10
@Quinn-With-Two-Ns Quinn-With-Two-Ns force-pushed the NEXUS-283 branch 2 times, most recently from 91ef578 to 2be8831 Compare April 7, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants